How does "index f2e4113..d4b9bfc 100644" in git diff ...

This form is to view the changes you made relative to the index (staging area for the next commit). In other words, the differences are what you could tell Git ...

Compare the content and mode of the blobs found in a tree object with the corresponding tracked files in the working tree, or with the corresponding paths ...

2015年12月14日 — Before running git diff --no-index , you may want to set diff.colorMoved in the Git config. Alternatively, you can include a --color-moved ...

When <path> arguments are present, compares only paths matching those patterns. Otherwise all tracked files are compared. OPTIONS. -p, -u, --patch Generate ...

Generate diffs with <n> lines of context instead of the usual three. Implies --patch. --output=<file>. Output to a specific file instead of stdout. -- ...

Compares the content and mode of the blobs found via a tree object with the content of the current index and, optionally ignoring the stat state of the file ...

2013年10月7日 — The reason the mode is 100644 rather than 660 or 100660 is that git stores only one bit of file rwx modes, specifically, the x bit. The mode of ...

2021年7月20日 — According to the official Git documentation, git diff is used to: “Show changes between the working tree and the index or a tree, changes ...

2014年6月13日 — git diff is more versatile and can compare two files, or two commits, or (like diff-index) a tree and the index. In your case, a diff HEAD would ...